Repository navigation
chore(release): publish v0.13.1 with casting runtime fix - #1900
bradygaster wants to merge 4 commits into
Conversation
Closes #1876 Co-authored-by: brady gaster <bradygaster@github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Closes #1876 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Closes #1876 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
🛫 PR Readiness Check
PR Scope: 📦🔧 Mixed (product + infrastructure)
|
| Status | Check | Details |
|---|---|---|
| ❌ | Single commit | 4 commits — consider squashing before review |
| ✅ | Not in draft | Ready for review |
| ✅ | Branch up to date | Up to date with main |
| ❌ | Copilot review | No Copilot review yet — it may still be processing |
| ✅ | Changeset present | CHANGELOG.md edit found |
| ✅ | Scope clean | No .squad/ or docs/proposals/ files |
| ✅ | No merge conflicts | No merge conflicts |
| ✅ | Copilot threads resolved | 1 active Copilot thread(s) resolved (1 outdated skipped) |
| ❌ | CI passing | 1 check(s) failing: test |
Files Changed (9 files, +95 −15)
| File | +/− |
|---|---|
CHANGELOG.md |
+6 −2 |
package-lock.json |
+4 −4 |
package.json |
+1 −1 |
packages/squad-cli/package.json |
+1 −1 |
packages/squad-sdk/package.json |
+1 −1 |
packages/squad-sdk/src/tools/index.ts |
+8 −1 |
packages/squad-sdk/templates/skills/coordinator-source-of-truth/SKILL.md |
+1 −1 |
test/cli/state-mcp.test.ts |
+49 −4 |
test/state-backend.test.ts |
+24 −0 |
Total: +95 −15
This check runs automatically on every push. Fix any ❌ items and push again.
See CONTRIBUTING.md and PR Requirements for details.
There was a problem hiding this comment.
🟡 Changes recommended
The release metadata approach introduces avoidable drift/duplication risk (changeset fragment + manual version/changelog) and the new runtime allowlist appears to conflict with existing source-of-truth documentation that should be updated in tandem.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Release bump to publish v0.13.1, promoting the casting runtime state allowlist fix so state-mcp can persist the coordinator-required casting keys via non-local backends.
Changes:
- Allow exactly
casting/policy.json,casting/registry.json, andcasting/history.jsonas mutable runtime state tool keys. - Add SDK + CLI integration coverage to ensure casting state writes go through
orphanandtwo-layerbackends without mutating the worktree. - Bump versions to 0.13.1 and add the corresponding root changelog entry.
File summaries
| File | Description |
|---|---|
| test/state-backend.test.ts | Adds a regression test asserting only the 3 casting runtime keys are writable via state tools. |
| test/cli/state-mcp.test.ts | Adds MCP bridge coverage for writing/reading casting keys through both orphan and two-layer. |
| packages/squad-sdk/src/tools/index.ts | Extends validateMutableStateToolKey to allow exactly the 3 casting keys; updates error text. |
| packages/squad-sdk/package.json | Bumps SDK version to 0.13.1. |
| packages/squad-cli/package.json | Bumps CLI version to 0.13.1. |
| package.json | Bumps repo version to 0.13.1. |
| package-lock.json | Aligns lockfile workspace versions with 0.13.1. |
| CHANGELOG.md | Adds 0.13.1 release notes entry describing the casting runtime state fix. |
| .changeset/casting-runtime-state.md | Adds a changeset fragment for the casting runtime state fix. |
Review details
- Files reviewed: 8/9 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Closes #1876 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
The allowlist change is narrowly scoped, aligns docs/tests with behavior, and the added regression coverage directly exercises the release-critical paths.
Review details
- Files reviewed: 8/9 changed files
- Comments generated: 0 new
- Review effort level: Lite
Summary
Evidence
Merging triggers the documented release workflow on main, creating v0.13.1 and publishing both npm packages.
Closes #1876